Skip to content

ci: a release is marked the latest, as the repository's newest - #45

Merged
Xenolphthalein merged 1 commit into
common/7.2from
ci/release-latest
Nov 16, 2026
Merged

Xenolphthalein merged 1 commit into
common/7.2from
ci/release-latest

Conversation

@Xenolphthalein

Copy link
Copy Markdown
Contributor

GitHub marks one release of a repository the latest. The release job created every release with --latest=false (several headsets share the repository), so phoenix/7.2-1, published before that, kept the mark while phoenix/7.2-4 is the newest. The job now passes --latest: the newest release, of whichever headset, is the latest; each headset's repository still pins its own tag. phoenix/7.2-4 is marked by hand.

…b's one latest, which phoenix/7.2-1 kept since releases stopped taking it
@Xenolphthalein
Xenolphthalein merged commit b61d4ac into common/7.2 Nov 16, 2026
5 checks passed
@Xenolphthalein
Xenolphthalein deleted the ci/release-latest branch November 16, 2026 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant